feat(install): cursor --mode local|marketplace + hooks-registration doctor findings (#407) - #414

…pts prompt hooks

Address Codex review on #414:
- Drop the unsupported `version` field from the staged marketplace.json
  plugin entry (pinned schema is additionalProperties: false); the version
  stays in plugins/<name>/.cursor-plugin/plugin.json. Tests validate the
  staged manifest against the pinned schema.
- Idempotency check also verifies the staged marketplace.json matches the
  generated manifest (helper and emitted install.mjs).
- AB7321 accepts `{ type: "prompt", prompt }` hook entries; only command
  entries get script-path checks.
- AB7323 only consults the staged marketplace's own plugins/cache partition.

…ble staging root

Address Codex review round 2 on #414:
- AB7323 marks a staged repository corrupt when marketplace.json does not
  list <entry> at plugins/<entry>, instead of reporting import state.
- An unreadable ~/.cursor/agent-bundle/marketplaces becomes an AB7323 error
  finding rather than aborting `doctor --host cursor`.

…plete; propagate corrupt staging

Address Codex review round 3 on #414:
- install.mjs uses the same `description ?? name` fallback as the emitted
  Cursor manifest so both install entry points stage byte-identical
  marketplace.json (no spurious AB7005 across entry points).
- AB7321 parses hook documents through the pinned hooks.schema.json (Ajv),
  so unknown events / extra properties / empty command or prompt never
  report `registered`.
- AB7323 only treats a cache entry with Cursor's `.cache-complete` receipt
  as an import.
- `doctor --from` surfaces a `corrupt` staged marketplace instead of
  collapsing it to `unregistered`.

…ok matching

Address Codex review round 4 on #414:
- AB7323 only accepts a receipted cache entry whose segment matches the
  staged HEAD commit (or plugin version when the commit is unknown), and
  skips malformed cache entries instead of aborting Doctor.
- The staged plugins/<entry>/.cursor-plugin/plugin.json must be named
  <entry>, otherwise the repository is corrupt.
- AB7322 matches plugin paths on a component boundary so a sibling plugin
  with a shared path prefix is not flagged as duplicate delivery.

…lvable HEAD, label reruns as staged

Address Codex review round 5 on #414:
- AB7323 validates marketplace.json against the full pinned schema and
  requires .git/HEAD to resolve to a commit SHA; otherwise `corrupt`.
- AB7322 accepts `\` as a path-component boundary for Windows commands.
- Shared install formatter prints "Already staged" for a repeated
  marketplace-mode run (matching install.mjs) instead of "Already installed".

…d repo with missing plugin copy

Address Codex review round 6 on #414:
- AB7323 cache lookup uses the plugin version segment only when no staged
  commit is known; with a known HEAD only that commit's receipt counts.
- `doctor --from` inspects a present staged repository whose plugins/<name>
  copy is gone and reports `corrupt` with the AB7323 repair step instead of
  AB7307 "not installed".

…son; harden hook-path checks

Address Codex review round 7 on #414:
- Marketplace staging uses `git add --all --force` (helper and install.mjs)
  so bundle-internal .gitignore/global excludes cannot drop files from the
  commit Cursor imports.
- AB7323 validates the staged plugins/<entry>/.cursor-plugin/plugin.json
  against the pinned plugin schema; HEAD must be exactly 40 or 64 hex.
- AB7321 hook-target probe tolerates ENOTDIR/EACCES (reports stale).
- AB7322 resolves relative/`~/` user-hook command tokens against ~/.cursor
  before the plugin-path boundary check.

…pts prompt hooks

Address Codex review on #414:
- Drop the unsupported `version` field from the staged marketplace.json
  plugin entry (pinned schema is additionalProperties: false); the version
  stays in plugins/<name>/.cursor-plugin/plugin.json. Tests validate the
  staged manifest against the pinned schema.
- Idempotency check also verifies the staged marketplace.json matches the
  generated manifest (helper and emitted install.mjs).
- AB7321 accepts `{ type: "prompt", prompt }` hook entries; only command
  entries get script-path checks.
- AB7323 only consults the staged marketplace's own plugins/cache partition.

…ble staging root

Address Codex review round 2 on #414:
- AB7323 marks a staged repository corrupt when marketplace.json does not
  list <entry> at plugins/<entry>, instead of reporting import state.
- An unreadable ~/.cursor/agent-bundle/marketplaces becomes an AB7323 error
  finding rather than aborting `doctor --host cursor`.

…plete; propagate corrupt staging

Address Codex review round 3 on #414:
- install.mjs uses the same `description ?? name` fallback as the emitted
  Cursor manifest so both install entry points stage byte-identical
  marketplace.json (no spurious AB7005 across entry points).
- AB7321 parses hook documents through the pinned hooks.schema.json (Ajv),
  so unknown events / extra properties / empty command or prompt never
  report `registered`.
- AB7323 only treats a cache entry with Cursor's `.cache-complete` receipt
  as an import.
- `doctor --from` surfaces a `corrupt` staged marketplace instead of
  collapsing it to `unregistered`.

…ok matching

Address Codex review round 4 on #414:
- AB7323 only accepts a receipted cache entry whose segment matches the
  staged HEAD commit (or plugin version when the commit is unknown), and
  skips malformed cache entries instead of aborting Doctor.
- The staged plugins/<entry>/.cursor-plugin/plugin.json must be named
  <entry>, otherwise the repository is corrupt.
- AB7322 matches plugin paths on a component boundary so a sibling plugin
  with a shared path prefix is not flagged as duplicate delivery.

…lvable HEAD, label reruns as staged

Address Codex review round 5 on #414:
- AB7323 validates marketplace.json against the full pinned schema and
  requires .git/HEAD to resolve to a commit SHA; otherwise `corrupt`.
- AB7322 accepts `\` as a path-component boundary for Windows commands.
- Shared install formatter prints "Already staged" for a repeated
  marketplace-mode run (matching install.mjs) instead of "Already installed".

…d repo with missing plugin copy

Address Codex review round 6 on #414:
- AB7323 cache lookup uses the plugin version segment only when no staged
  commit is known; with a known HEAD only that commit's receipt counts.
- `doctor --from` inspects a present staged repository whose plugins/<name>
  copy is gone and reports `corrupt` with the AB7323 repair step instead of
  AB7307 "not installed".

…son; harden hook-path checks

Address Codex review round 7 on #414:
- Marketplace staging uses `git add --all --force` (helper and install.mjs)
  so bundle-internal .gitignore/global excludes cannot drop files from the
  commit Cursor imports.
- AB7323 validates the staged plugins/<entry>/.cursor-plugin/plugin.json
  against the pinned plugin schema; HEAD must be exactly 40 or 64 hex.
- AB7321 hook-target probe tolerates ENOTDIR/EACCES (reports stale).
- AB7322 resolves relative/`~/` user-hook command tokens against ~/.cursor
  before the plugin-path boundary check.

…lvable HEAD, label reruns as staged

Address Codex review round 5 on #414:
- AB7323 validates marketplace.json against the full pinned schema and
  requires .git/HEAD to resolve to a commit SHA; otherwise `corrupt`.
- AB7322 accepts `\` as a path-component boundary for Windows commands.
- Shared install formatter prints "Already staged" for a repeated
  marketplace-mode run (matching install.mjs) instead of "Already installed".

…d repo with missing plugin copy

Address Codex review round 6 on #414:
- AB7323 cache lookup uses the plugin version segment only when no staged
  commit is known; with a known HEAD only that commit's receipt counts.
- `doctor --from` inspects a present staged repository whose plugins/<name>
  copy is gone and reports `corrupt` with the AB7323 repair step instead of
  AB7307 "not installed".

…son; harden hook-path checks

Address Codex review round 7 on #414:
- Marketplace staging uses `git add --all --force` (helper and install.mjs)
  so bundle-internal .gitignore/global excludes cannot drop files from the
  commit Cursor imports.
- AB7323 validates the staged plugins/<entry>/.cursor-plugin/plugin.json
  against the pinned plugin schema; HEAD must be exactly 40 or 64 hex.
- AB7321 hook-target probe tolerates ENOTDIR/EACCES (reports stale).
- AB7322 resolves relative/`~/` user-hook command tokens against ~/.cursor
  before the plugin-path boundary check.

… relative hook script/path handling

Address Codex review round 8 on #414:
- Changeset bump is `patch` (pre-1.0: minor = breaking).
- Marketplace rerun refuses when the staged working tree differs from the
  committed HEAD Cursor would import (helper and install.mjs).
- AB7321 checks every `./`- or `${CURSOR_PLUGIN_ROOT}`-relative token of a
  hook command (e.g. `node ./hooks/run.mjs`), not just the executable.
- AB7322 resolves `.\`/`..\` Windows-relative user-hook tokens too.

#428)

Document the user-facing behaviour that landed on main after the docsite
PR (#384) merged, in both locales:

- install: `agent-bundle install cursor --mode local|marketplace` and the
  Doctor findings for Cursor hook registration and marketplace staging
  (AB7322-AB7324) (#414)
- project structure: per-host feature sets for src/commands and src/rules,
  with AB4907/AB4908 and AB4927/AB4928 (#427)
- testing: the script-dispatch and workbench-surface proof levels, eleven in
  all, and the routed cli-tool template (#398)
- notices reference: inbox and resources/updated wiring gated on the host's
  noticeDelivery advertisement (#412, #376)